Fixes in the AArch64 nofp variants regarding RTTI and exceptions #594
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch fixes a few issues in the AArch64 nofp variants:
AArch64 nofp variants without exceptions and RTTI must have higher priority
The presence of
-fno-exceptionsand-fno-rttiin the driverinvocation causes matching with two variants: the one with
RTTI/Exceptions and the one without.
In the multilib system, the last match is the one that wins, therefore
in the JSON file we must list the variant without RTTI/Exceptions
after the one with.
Enable exceptions and RTTI in the build of aarch64 nofp variants supposed to have them